Data model of participation in multi-channel and multi-party contacts

ABSTRACT

The present invention is directed to a contact center that includes a switching fabric  110, 130  operable to configure a communication session between a first customer and a first resource  138  for servicing of a first contact by the first resource and a contact tracking agent  232  operable, during the servicing of the first contact by the first resource, to (a) monitor the first contact center endpoint for at least one of (i) a change in contact state, (ii) the connection of the first resource and the first customer through a second (new) communication channel, and (iii) the addition of a party to and/or removal of a party from the communication session and (b), when the at least one of (i)-(iii) occurs, terminate a first contact part and create a second contact part. The first and second contact parts are associated with the communication session.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefits under 35 U.S.C. §119 of U.S. Provisional Patent Application Ser. No. 60/558,613, filed Mar. 31, 2004, of the same title and to the same inventors, which is incorporated herein by this reference.

FIELD OF THE INVENTION

The present invention is directed generally to contact center management and specifically to monitoring selected contact center events.

BACKGROUND OF THE INVENTION

Contact centers, such as Automatic Call Distribution or ACD systems, are employed by many enterprises to service customer contacts. A typical contact center includes a switch and/or server to receive and route incoming packet-switched and/or circuit-switched contacts and one or more resources, such as human agents and automated resources (e.g., Interactive Voice Response (IVR) units), to service the incoming contacts. Contact centers distribute contacts, whether inbound or outbound, for servicing to any suitable resource according to predefined criteria. In many existing systems, the criteria for servicing the contact from the moment that the contact center becomes aware of the contact until the contact is connected to an agent are customer-specifiable (i.e., programmable by the operator of the contact center), via a capability called call vectoring. Normally in present-day ACDs when the ACD system's controller detects that an agent has become available to handle a call, the controller identifies all predefined call-handling skills of the agent (usually in some order of priority) and delivers to the agent the highest-priority oldest-waiting call that matches the agent's highest-priority skill. Generally, the only condition that results in a call not being delivered to an available agent is that there are no calls waiting to be handled.

Most present-day contact-distribution algorithms focus on being “fair” to contactors and agents. This fairness is reflected by the standard first-in, first-out call to most-idle-agent assignment algorithm. Skills-based routing improves upon this basic algorithm in that it allows each agent to be slotted into a number of categories (splits) based on the agent's skill types and levels.

The primary objective of contact center management, including call-distribution algorithms, is to ultimately maximize call center performance and profitability. That may involve minimizing cost, maximizing call throughput, and/or maximizing revenue, among others. For example, when a new call arrives, the call should be handled by an agent who either has the ability to produce the most revenue or can handle the call in the shortest amount of time. Also, when an agent becomes available to handle a new call, the agent should handle either the call that has the possibility of generating the most revenue or the call which the agent is most efficient in handling.

To realize the objectives of optimized contact center performance and profitability, various algorithms have been developed to monitor and track selected contact center events. For example, the Services for Computer Supported Telecommunications Applications (CSTA) standard 269 of the European Computer Manufacturers Association (ECMA) defines relationships among calls, connections, and devices. The CSTA standard specifies that the identification of a call changes when the call is conferenced or transferred and that a “call”, whether it represents voice, email, or messaging, involves only a single channel. The CSTA standard does not specify how calls, connections, and devices are to be tracked for reporting. It only specifies the states of calls, connections and devices before and after the operations it defines and the events that are emitted as a result of the operations. Current Avaya™ Customer Resource Management™ products, such as Basic Call Management System or BCMS™, Call Management System or CMS™, and Operational Analyst™, have data models that provide only limited details. BCMS has only a summary of the total time that calls spent on hold at an agent. It has neither further detail on the calls held nor information on conferences and transfers in its call record structure. CMS has more detailed information on held calls, conferences, and transfers in its call record structure. CMS tracks which agent held a call, how many times and for how long, when there is more than one agent on a call. However, CMS does not record when the call was put on hold by which participants and when the call was removed from hold by each party. Avaya's Multi-Media Contact Center™ tracks summary data, in a manner similar to CMS, and has a data model supporting detailed tracking of contacts as well. The data model does not support tracking for conferences involving multiple external parties nor for multi-channel contacts. In short, none of BCMS, CMS, or the Multi-Media Contact Center addresses multi-channel or multi-state contact tracking, since they are generally directed to voice contacts. Finally, existing data warehouse models in the data warehousing industry provide, at most, only limited information on contacts. Existing models tend to focus on customer and billing information from sales and marketing systems but typically do not contain structures that support interaction details. The models fail to provide the granular details that will allow contact centers to analyze the details of individual contacts.

There is a need for a contact monitoring/tracking algorithm that provides details on contact history in a contact center, including details on changes in state and channel during the customer/contact center interaction.

SUMMARY OF THE INVENTION

These and other needs are addressed by the various embodiments and configurations of the present invention. The present invention is generally directed to a method for tracking multi-channel and/or multi-party contacts. A “contact” refers to an interaction between selected parties/entities over one or more channels. The parties/entities can be human, such as a customer, agent, and supervisor, or nonhuman, such as an Interactive Voice Response unit, a Web server, content analyzer, email server, and the like.

In one embodiment, a contact center is provided that includes:

(a) a plurality of resources (e.g., human agents, automated entities such as an IVR unit, etc.) for servicing a plurality of inbound and/or outbound customer contacts;

(b) a switching fabric (e.g., a switch and/or server) for configuring a communication session (e.g., a live voice call, instant messaging session, and chat session) between a first customer and a first resource for servicing of the first customer's contact by the first resource; and

(c) a contact tracking agent that, during the servicing of the first customer by the first resource, monitors the first resource's endpoint for the occurrence of one or more of (i) a change in contact state, (ii) the connection of the first resource and the first customer through a new communication channel, and (iii) the addition of a party to and/or removal of a party from the communication session and, when one or more of the above events occurs, terminates a first contact part and creates a second contact part.

The channel/communication medium used by the contact refers to a communication technique, pathway, or method as defined, governed, or enabled by one or more selected protocols (e.g., a packet-based protocol such as TCP/IP, RTP, and RTCP, an asynchronous transfer mode protocol, and a frame relay protocol or a circuit-switched protocol), algorithms (e.g., software applications, such as E-mail, Web browsers, instant messaging, text chat, Integrated Services Digital Network or ISDN, QSIG, DPNSS, SIP, H.323, VDP, and SGCP, etc.) switches or routers, and/or communication medium (e.g., twisted wire, coaxial cable, fiber optic cable, wireless, cellular, and PCS™ of U.S. Sprint). For example, voice-only wired telephone communications over the PSTN represent one channel, voice-over-IP telephony yet another channel, voice-only wireless telephone communications a further channel, non-voice IP telephony (e.g., a text web chat) a further channel, multi-media telephony (e.g., a video stream, an audio/video call, etc.) over the PSTN a further channel, instant messaging over the data network a further channel, a Web conference over the Internet a further channel, e-mail over the data network a further channel, a facsimile over a circuit-switched or packet-switched medium a further channel, etc.

The “state” of a contact refers to the existing or current condition or status of a contact, such as active, inactive, enqueued (or in queue), ringing, on hold, and, terminating.

A “contact part” represents a single party, contact state and/or communication channel in a contact or communication session. Typically, the contact part is based collectively on a single party, contact state, and channel. A contact part can thus be the smallest measurable part of a communication. Typically, a new contact part is created, and a prior contact part terminated, whenever a monitored party and/or channel is added or dropped and/or experiences a state change. In contrast, the contact maintains its identification throughout its lifetime, regardless of the number of parties and channels that are involved. At least one (and probably more) contact part(s) is/are created for every party/endpoint in the contact, including customers, agents, automated resources, and any other entity that participates in the contact. In other words, each endpoint to the contact or communication session is commonly monitored independently and separately. Thus, a first endpoint in a communication session can have a first contact part and a second endpoint in the same communication session can have a second contact part that temporally overlaps the first contact part. The use of a contact part can allow tracking the time that each party in the contact spends communicating and on hold (or the equivalent) as well as providing the complete picture of who joined the contact, at what point, and for how long.

Using the concept of the “contact part”, other data structures can be created to provide more detail in tracking the contact. For example, a “contact part related” refers to the relationship of two contact parts. “Contact part related” shows the reason for the relationship, particularly if one contact part generated the next contact part. It is typically used to capture the cause and effect between two contact parts. A “contact media interaction” refers to the media-specific characteristics of a contact.

The present invention can provide a number of advantages over the prior art. For example, the contact part provides a complete and detailed record of all states, participants, and channels involved in a given contact from the time the contact reaches or is launched by a contact center until it is terminated. The contact part and related entities thus allow accurate and detailed reporting of complex interactions with regard to the involvement of each party and communication channel. Examples of such contacts include conference calls where parties join and leave the conference during the course of the contact and voice chat sessions where parties add and drop the voice channel to an existing Web chat. As noted, conventional architectures generally provide either summary reporting (such as the number of times an agent held a call) or detailed reporting only on certain parties involved in such interactions. The prior does not track multi-party contacts. Additionally, the present invention can support reporting at higher levels with less detail that may be more comprehensible to users of reports than the low-level detail captured. The ability to accurately track multi-party and multi-channel contacts can enable contact center administrators and managers to identify not only more effective and/or inexpensive ways to service customer contacts but also more effective ways to manage limited contact center resources.

These and other advantages will be apparent from the disclosure of the invention(s) contained herein.

The above-described embodiments and configurations are neither complete nor exhaustive. As will be appreciated, other embodiments of the invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a contact center according to an embodiment of the present invention;

FIG. 2 is a block diagram of a server according to an embodiment of the present invention;

FIGS. 3A, B and C are collectively a third normal form data model depicting the data structures of an embodiment of the present invention;

FIG. 4 is a flow chart depicting an operational embodiment of the contact tracking agent;

FIGS. 5A and B depict a first example of an operational embodiment of the contact tracking agent; and

FIGS. 6A and B depict a second example of an operational embodiment of the contact tracking agent.

DETAILED DESCRIPTION

The invention will be illustrated below in conjunction with an exemplary communication system. Although well suited for use with, e.g., a system having an ACD or other similar contact processing switch, the invention is not limited to use with any particular type of communication system switch or configuration of system elements. Those skilled in the art will recognize that the disclosed techniques may be used in any communication application in which it is desirable to provide improved contact processing.

FIG. 1 shows an illustrative embodiment of the present invention. A contact center 100 comprises a central server 110, a set of data stores or databases 114 containing contact or customer related information and other information that can enhance the value and efficiency of the contact processing, and a plurality of servers, namely a voice mail server 118, an Interactive Voice Response unit or IVR 122, and other servers 126, a switch 130, a plurality of working agents operating packet-switched (first) telecommunication devices 134-1 to N (such as computer work stations or personal computers), and/or circuit-switched (second) telecommunication devices 138-1 to M, all interconnected by a local area network LAN (or wide area network WAN) 142. The servers can be connected via optional communication lines 146 to the switch 130. As will be appreciated, the other servers 126 can also include a scanner (which is normally not connected to the switch 130 or Web server), VoIP software, video call software, voice messaging software, an IP voice server, a fax server, a web server, and an email server) and the like. The switch 130 is connected via a plurality of trunks 150 to the Public Switch Telecommunication Network or PSTN 154 and via link(s) 152 to the second telecommunication devices 138-1 to M. A gateway 158 is positioned between the server 110 and the packet-switched network 162 to process communications passing between the server 110 and the network 162.

The term “switch” or “server” as used herein should be understood to include a PBX, an ACD, an enterprise switch, or other type of telecommunications system switch or server, as well as other types of processor-based communication control devices such as media servers, computers, adjuncts, etc.

Referring to FIG. 2, one possible configuration of the server 110 is depicted. The server 110 is in communication with a plurality of customer communication lines 200 a-y (which can be one or more trunks, phone lines, etc.) and agent communication line 204 (which can be a voice-and-data transmission line such as LAN 142 and/or a circuit switched voice line 140). The server 110 can include a Basic Call Management System™ or BCMS 224 and a Call Management System™ or CMS 228 that gathers call records and contact-center statistics for use in generating contact-center reports. CMS and BCMS and any other reporting system, such as Operational Analyst™ will hereinafter be referred to jointly as CMS 228.

The switch 130 and/or server 110 can be any architecture for directing contacts to one or more telecommunication devices. Illustratively, the switch and/or server can be a modified form of the subscriber-premises equipment disclosed in U.S. Pat. Nos. 6,192,122; 6,173,053; 6,163,607; 5,982,873; 5,905,793; 5,828,747; and 5,206,903, all of which are incorporated herein by this reference; Avaya Inc.'s Definity™ Private-Branch Exchange (PBX)-based ACD system; MultiVantage™ PBX, CRM Central 2000 Server™, Communication Manager™, S8300™ media server, and/or Avaya Interaction Center™. Typically, the switch/server is a stored-program-controlled system that conventionally includes interfaces to external communication links, a communications switching fabric, service circuits (e.g., tone generators, announcement circuits, etc.), memory for storing control programs and data, and a processor (i.e., a computer) for executing the stored control programs to control the interfaces and the fabric and to provide automatic contact-distribution functionality. The switch and/or server typically include a network interface card (not shown) to provide services to the serviced telecommunication devices. Other types of known switches and servers are well known in the art and therefore not described in detail herein.

Referring to FIG. 2, included among the data stored in the server 110 is a set of contact queues 208 a-n and a separate set of agent queues 212 a-n. Each contact queue 208 a-n corresponds to a different set of agent skills, as does each agent queue 212 a-n. Conventionally, contacts are prioritized and either are enqueued in individual ones of the contact queues 208 a-n in their order of priority or are enqueued in different ones of a plurality of contact queues that correspond to a different priority. Likewise, each agent's skills are prioritized according to his or her level of expertise in that skill, and either agents are enqueued in individual ones of agent queues 212 a-n in their order of expertise level or are enqueued in different ones of a plurality of agent queues 212 a-n that correspond to a skill and each one of which corresponds to a different expertise level. Included among the control programs in the server 110 is a contact vector 216. Contacts incoming to the contact center are assigned by contact vector 216 to different contact queues 208 a-n based upon a number of predetermined criteria, including customer identity, customer needs, contact center needs, current contact center queue lengths, customer value, and the agent skill that is required for the proper handling of the contact. Agents who are available for handling contacts are assigned to agent queues 212 a-n based upon the skills that they possess. An agent may have multiple skills, and hence may be assigned to multiple agent queues 212 a-n simultaneously. Furthermore, an agent may have different levels of skill expertise (e.g., skill levels 1-N in one configuration or merely primary skills and secondary skills in another configuration), and hence may be assigned to different agent queues 212 a-n at different expertise levels. Call vectoring is described in DEFINITY Communications System Generic 3 Call Vectoring/Expert Agent Selection (EAS) Guide, AT&T publication no. 555-230-520 (Issue 3, November 1993). Skills-based ACD is described in further detail in U.S. Pat. Nos. 6,173,053 and 5,206,903.

Referring to FIG. 1, the gateway 158 can be Avaya Inc.'s, G700 Media Gateway™ and may be implemented as hardware such as via an adjunct processor (as shown) or as a chip in the server.

The first telecommunication devices 134-1, . . . 134-N are packet-switched and can include, for example, IP hardphones such as the Avaya Inc.'s, 4600 Series IP Phones™, IP softphones such as Avaya Inc.'s, IP Softphone™, Personal Digital Assistants or PDAs, Personal Computers or PCs, laptops, packet-based H.320 video phones and conferencing units, packet-based voice messaging and response units, packet-based traditional computer telephony adjuncts, and any other communication device.

The second telecommunication devices 138-1, . . . 138-M are circuit-switched. Each of the telecommunication devices 138-1, . . . 138-M corresponds to one of a set of internal extensions Ext₁, . . . ExtM, respectively. These extensions are referred to herein as “internal” in that they are extensions within the premises that are directly serviced by the switch. More particularly, these extensions correspond to conventional telecommunication device endpoints serviced by the switch/server, and the switch/server can direct incoming calls to and receive outgoing calls from these extensions in a conventional manner. The second telecommunication devices can include, for example, wired and wireless telephones, PDAs, H.320 video phones and conferencing units, voice messaging and response units, traditional computer telephony adjuncts, and any other communication device.

It should be noted that the invention does not require any particular type of information transport medium between switch or server and first and second telecommunication devices, i.e., the invention may be implemented with any desired type of transport medium as well as combinations of different types of transport channels.

The packet-switched network 162 can be any data and/or distributed processing network, such as the Internet. The network 162 typically includes proxies (not shown), registrars (not shown), and routers (not shown) for managing packet flows.

The packet-switched network 162 is in communication with an external first telecommunication device 174 via a gateway 178, and the circuit-switched network 154 with an external second telecommunication device 180. These telecommunication devices are referred to as “external” in that they are not directly supported as telecommunication device endpoints by the switch or server. The telecommunication devices 174 and 180 are an example of devices more generally referred to herein as “external endpoints.”

In a preferred configuration, the server 110, network 162, and first telecommunication devices 134 are Session Initiation Protocol or SIP compatible and can include interfaces for various other protocols such as the Lightweight Directory Access Protocol or LDAP, H.248, H.323, Simple Mail Transfer Protocol or SMTP, IMAP4, ISDN, E1/T1, and analog line or trunk.

It should be emphasized that the configuration of the switch, server, user telecommunication devices, and other elements as shown in FIG. 1 is for purposes of illustration only and should not be construed as limiting the invention to any particular arrangement of elements.

As will be appreciated, the central server 110 is notified via LAN 142 of an incoming contact by the telecommunications component (e.g., switch 130, fax server, email server, web server, and/or other server) receiving the incoming contact. The incoming contact is held by the receiving telecommunications component until the server 110 forwards instructions to the component to forward or route the contact to a specific contact center resource, such as the IVR unit 122, the voice mail server 118, and/or first or second telecommunication device 134, 138 associated with a selected agent. The server 110 distributes and connects these contacts to telecommunication devices of available agents based on the predetermined criteria noted above. When the central server 110 forwards a voice contact to an agent, the central server 110 also forwards customer-related information from databases 114 to the agent's computer work station for viewing (such as by a pop-up display) to permit the agent to better serve the customer. The agents process the contacts sent to them by the central server 110. This embodiment is particularly suited for a Customer Relationship Management (CRM) environment in which customers are permitted to use any media to contact a business. In a CRM environment, both real-time and non-real-time contacts must be handled and distributed with equal efficiency and effectiveness.

According to the invention, included among the programs executing on the server 110 is a contact tracking agent 232. The agent 232 is stored either in the main memory or in a peripheral memory (e.g., disk, CD ROM, etc.) or some other computer-readable medium of the center 100. The agent 232 collects detailed information on incoming and/or outgoing contacts in the contact center using the concept of a “contact part”. A “contact” is composed of one or more contact parts and maintains its identification throughout its lifetime, regardless of the number of parties, states, and channels involved. The actions of each party or endpoint are monitored independently to identify the addition/removal of parties and/or channel and state changes. The collected granular contact details can be analyzed by the CMS and provided to contact center management in a user configurable reports that can be used to maximize contact center efficiency.

A selected endpoint to a contact generally has one or associated contact parts during the course of the contact. For a selected endpoint, a new contact part is created and a current contact part is terminated when a party and/or channel is added and/or dropped and a state changes. Examples of activities or events that will result in multiple contact parts for a contact, include the contact changes state from “created” to “qualification”, a text chat contact becomes voice chat by adding voice transfers, an additional party is conferenced into an existing contact, and an existing contact is transferred from one agent to another agent.

The concept of a contact part gives rise to several related data entities, including contact part related, contact participation group, contact part purpose, contact part related reason, contact media interaction, contact media interaction disposition, contact part qualifier, contact part delivery source, contact part disposition, contact part routing method, contact part wait treatment, contact qualifier, dialed number purpose, disposition, media, party login, routing construct, routing construct contact part, state reason, step, and step contact part.

The relationships among these objects are illustrated in FIGS. 3A, 3B and 3C, which are collectively a third normal form data model of the objects and their respective attributes. As will be appreciated, interconnecting dashed and solid lines indicate the related entities and the type of relationship.

As can be seen from the figures, the attributes for contact 300 include contact ID (an internally generated unique identifier of a contact); contact type code (which identifies the type of contact), outbound contact initiation method, customer ID (the identifier(s) of the customer(s) engaged in the contact), data source ID, party ID (the identifier(s) of the parties to the contact), business role code, party role start datetime (the date/time that the system recognizes that the party may play a role in interactions with the enterprise), contact direction code, and contact direction description.

The attributes for contact part 304 include contact type code, media code (which identifies the type of media/medium used during the contact part), contact part ID (which uniquely identifies the contact part), contact ID (which uniquely identifies the contact of which the contact part is a subpart), state ID (which identifies the state of the corresponding monitored endpoint to which the contact part corresponds), contact media interaction start datetime (the date/time that the contact media interaction started), party ID, business role code, party role start datetime, wait treatment ID, active media mask (a mapping of possible media types and their direction), contact part delivery source code, UCID (Universal Call Identifier), contact part datetime started (the date/time that the contact part started), contact part datetime stopped (the date/time that the contact part stopped), observing call flag, trunk ID, contact part routing method code, contact part purpose code, extension ID, routing construct ID, contact part subject (a text description of the subject of the message), contact participation group ID, contact direction code, malicious call flag, queue priority, login ID, login start date/time, data source ID, reschedule datetime (time stamp indicating when the contact connected to this part will be rescheduled to make another attempt), contact control indicator, state reason ID, calling number ID (the number dialed by the originator of the contact), and dialed number purpose ID.

A contact part related 308 refers to or describes the relationship of two contact parts. It shows not only the relationship between two related contact parts but also the reason for the relationship, particularly when a first contact part generated (or immediately preceded) a second contact part. For example, the contact part related would link or associate first and second contact parts that emanated from the same contact. The attributes for contact part related 308 include contact part ID (which uniquely identifies the associated contact part(s)), child contact part ID (which uniquely identifies the contact part(s) (if any) immediately succeeding or generated from the subject contact part), state ID, contact ID, contact type code, media code, contact media interaction start datetime, party ID, business role code, party role start datetime, contact part related create datetime (the date/time when the contact part related was created), and contact part related reason code.

A contact participation group 312 identifies the simultaneous participation of multiple parties in a contact. It also distinguishes between instances of simultaneous participation in a contact. For example, a single contact may involve one or more conferences between differing sets of individuals. The contact participation group identifies all of the contact parts that were part of or emanated from the same contact. The contact part differs from the contact participation group in that the contact participation group shows the relationship of all contact parts in a group or set of contact parts, such as the participation of five parties in the same conference call or if the same contact involves multiple conferenced calls. All of the members in a group of contact parts are included in the contact participation group with a reason for their participation in the conference. Contact part related, in contrast, may show that the relationship between the hosting party's contact part and one of the conferee's contact part had a reason of added to conference or dropped from the conference for the relationship. By way of illustration of the differences between the two objects, when a party is added to a conference, the party will join the existing contact group that represents the same conference, and a contact part related instance is created to show that that individual contact part was added to the contact part that represents the host of the conference. The attributes for contact participation group 312 include contact participation group ID (a code uniquely identifying the associated contact participation group), contact participation group type code (a code corresponding to the type of contact participation group (e.g., multi-party conference)), contact participation group description (a text description of the contact participation group and is generally used to provide the business context in relation to the specific contact), and source system contact participation group ID.

Contact part purpose 316 classifies the purpose of the contact part, such as business, and personal, and contact part related reason 320 provides the reason that a first contact part is related to a second contact part, such as conference, and transfer. The attributes for contact part purpose 316 include contact part purpose code (which identifies the corresponding purpose of the contact part) and contact segment purpose description (which is a text description of the contact segment purpose). The attributes for contact part related reason 320 include contact part related reason code (which identifies the corresponding contact part related reason) and contact part related reason description (which is a text description of the reason for contact part relationships).

Contact media interaction 324 describes the media-specific characteristics of a contact. When there is more than one medium or sets of media associated with a given contact at different times, there is typically more than one contact media interaction associated with the contact. There may also be more than one contact media interaction for the same medium during a contact when the use of the medium is temporally discontinuous during the contact. By way of example, for email it is allowed and probable that there will be more than one media interaction using the same medium (email) for a single contact. This is possible because of tracking information that is carried in the email subject line that links “sends” with “replies”. A media interaction starts when at least one party begins using a medium to process a contact. The media interaction continues as long as any party involved in the contact is using the medium continuously. The media interaction ends when all parties involved in the contact are no longer using the medium. The attributes for contact media interaction 324 include contact ID, contact type code, media code, contact media interaction start datetime (the date/time that the contact media interaction started), language code, email header, email subject, email text, voice calling telephone number (the number of the calling telephone), voice called number, chat username, media protocol, email tracking number (an identifier used to track a thread of emails), email message ID (a unique identifier of an email message), and contact media interaction stop datetime (the date/time that the contact media interaction stopped).

Contact media interaction disposition 326 is the disposition of an instance of using a specific media as part of a contact. For example an email is actually an extended conversation that the contact can stop and resume as a different contact when some action is taken. At each of these points, the Electronic Data Unit or EDU retires. So for example when an agent sends a question to a Subject Matter Expert or SME agent the email is completed until they get a response back. The task is then recreated as a different contact. What the contact media interaction disposition is intended for is for the transient state of the email at the end of the specific interaction. The attributes for contact media interaction disposition 326 include contact ID, contact type code, media code, contact media interaction start datetime (the date/time that the contact media interaction started), disposition code (which identifies the corresponding disposition), and contact media interaction disposition start datetime (the date/time that the contact media interaction disposition occurred).

Contact part contact qualifier 328 is the assignment of abilities or characteristics to an instance of a party taking part in a contact, and contact part delivery source 332 is the source of the contact as it relates to an enterprise network. A contact may have qualifiers before being assigned to a routing construct, and the contact may never be assigned to a routing construct. The contact part delivery source identifies whether the contact was generated from within the organization or from some external point. Examples of contact part delivery source include “internal” and “external”. The attributes for contact part contact qualifier 328 include contact part contact qualifier start datetime (the date/time that a qualifier applies to a contact part), contact qualifier ID, contact type code, media code, contact part ID, contact ID, state ID, contact media interaction start datetime, party ID, business role code, and party role start datetime (the date/time that a party may play a role in interactions with the enterprise network). The attributes for contact part delivery source 332 include contact part delivery source code and contact part delivery source description

Contact part disposition 330 refers to the business result of a contact part, such as sale made, order place, and abandoned from hold, and contact part routing method 334 is the source of the contact part. Examples of sources include transferred from another agent, a direct call to an agent, transferred from an outbound dialer, and routed by an ACD. The attributes for contact part disposition 330 include disposition code, contact part ID, state ID, contact ID, contact type code, media code, contact media interaction start datetime, party ID, business role code, party role start datetime, and contact part disposition start datetime (the date/time that the system recorded a contact part disposition). The attributes for contact part routing method 334 include contact part routing method code (which identifies the corresponding contact part routing method) and contact part routing method description (which is a text description of the routing method used for the contact part).

Contact qualifier 336 refers to a characteristic, skill or ability that classifies an individual in terms of handling of a contact. The qualifier may be the ability of the agent to handle customers with a characteristic or the characteristic as it applies to the customer. Qualifiers are used to segment customers and to discriminate among customers in the assignment of processing resources. The attributes for contact qualifier 336 include contact qualifier ID, contact qualifier name, acceptable service level, contact qualifier description, source system contact qualifier ID, and data source ID.

The dialed number purpose 338 refers to the business purpose assigned to the dialed number. For example, 1-800-555-1212 is assigned to platinum customers who were offered a special discount on product X. The attributes for dialed number purpose 338 include dialed number purpose ID and dialed number purpose.

Disposition 340 is a description of the business value of the result of the interaction. Examples include successful contact, failed contact attempt, sale made, order placed, and the like. The attributes for disposition 340 include disposition code, disposition description (a text description of the disposition), disposition group code, disposition type code, data source ID, and disposition explanation (a free form text description of the disposition to allow parties to enter additional discussion that explains the business result of a call).

Media 344 refers to the category of transport used for a contact. Examples include email, postal, voice, Web, and the like. The attributes for media 344 include media code, media description (a text description of the media), last name (the surname of the party), title (the title of the party), name type code, data source ID, and preferred name (the preferred name of the party).

Party login 346 refers to the logins used a party to access systems within the enterprise. The attributes for party login 346 include login ID, login start datetime, party ID, business role code, data source ID, party role start datetime, and login end datetime.

Routing construct 350 refers to a logical or physical location for the collection and routing of contacts to agents or to other routing constructs. Routing constructs include a hunt group, an extension group, a split, a skill, a service class, a queue, a job, and a VDN. The attributes for routing construct 350 include routing construct ID (which identifies the corresponding routing construct), switch ID (which identifies the routing switch), routing construct description, routing construct name, routing construct start date/time, routing construct end date/time, data source ID, routing construct type code, virtual queue ID, marketing event ID, campaign ID, routing construct real time indicator, estimated average handling time, party ID, business role code, and party role start datetime.

State reason 354 refers to the reason that a state 356 exists or comes into being. It is often used to provide additional explanation surrounding the transition to state. For example, a contact state of “terminated”, may occur due to an abandon, a disconnect, a transfer, or an email dismissal. In the example, “abandon”, “disconnect”, etc. will be the state reason. The attributes for state reason 354 include state reason ID and state reason description (a text description of the state reason). The attributes for state 356 include state ID, state group ID, state name, state created date/time (the date/time that the system recorded a new state), state description (a text description of the state), state type code, data source ID, and source system state ID.

Step 358 is the smallest unit of work in the business process hierarchy. A step may be any executable action taken within the system by a party that can be administered and/or recorded. It may span time, work and multiple contacts. Step 358 is the instance of the lowest level of a business process taking place. In other words, a step contains the details that result from discrete business activity. Examples of steps include process Joe Smith's individual loan application, provide standard product information, check Joe Smith's credit status, and communicate the decision to Joe Smith. The attributes for step 358 include step 1D (which identifies the corresponding step), work item ID (which identifies the corresponding work item), business process ID (which identifies the corresponding business process), step start datetime (the date/time that the system records the existence of a step), step close datetime (the date/time that the system recognizes that the step is closed), and data source ID.

Contact part wait treatment 362 refers to the wait treatment applied to the participant during a selected contact part; routing construct contact part 366 identifies the use of a routing construct to queue or deliver a contact part; and step contact part 368 refers to the association between a contact part and a step. Step contact parts record the details of a communication that may take place in the processing of a step. A single contact may be associated with many steps, and a step may be associated with many contact parts. As will be appreciated, other activity that does not require communication may occur in the processing of a step. The attributes for contact part wait treatment 362 include wait treatment ID (which identifies the corresponding wait treatment), wait treatment description (which is a text description of the wait treatment), source system wait treatment ID, and data source ID. The attributes for routing construct contact part 366 include routing construct contact part start datetime (the date/time that a contact part begins to be routed via a routing construct), a contact type code, a media code, a contact part ID, a contact ID, a state ID, a contact media interaction start datetime, a party ID, a business role code, a party role start datetime, a routing construct ID, a routing construct contact part end datetime (the date/time that a contact part's routing via a routing construct ends). The attributes for step contact part 368 include contact media interaction start datetime, contact ID, contact type code, media code, step 1D, contact part ID, state ID, party ID, business role code, party role start datetime (the date/time that a party may play a role in interactions with the enterprise), step contact part start datetime (the date/time that the system becomes aware that a contact part was associated with a step), and step contact part end datetime (the date/time that the system becomes aware that a contact part's association with a step ended).

The operation of the contact tracking agent 232 will now be described with reference to FIG. 4.

In step 400, the agent 232 initializes all pertinent variables.

In decision diamond 404, the agent 232 waits for a new contact to be received by the contact center 100. It is important to note that a “contact” includes an attempt to communicate between a party inside or outside of a contact center and a party inside the contact center. The attempt may or may not be successful. The contact normally begins when a party inside the contact center initiates an attempt to communicate (e.g., dials a call, sends an email, etc.) or when a party outside the center 100 reaches a measured or monitored entity in the center (e.g., a VDN, Web page, email server, etc.). The contact includes wrap up time. The contact is finished when the last party terminates participation and completes any wrap up work associated with the communication.

When a new contact is detected, the agent 232 in step 408 creates a contact part for each monitored endpoint and proceeds with monitoring each of the endpoints. In decision diamonds 412, 416, 420, respectively, the agent 232 determines if a change in state, media or party (endpoint) has taken place. If so, the agent 324, in step 424, creates a new contact part for the endpoint effecting the change. Typically, the contact part for the other endpoint is unaffected by the change. In other words, a change only impacts the monitored endpoint experiencing the change. If no change is detected or after step 424 is completed, the agent 232 determines, in decision diamond 428, whether the contact has terminated. If not, the agent 232 returns to decision diamond 412. If so, the agent 232 proceeds to decision diamond 404 and awaits a next (new) contact.

To illustrate the operation of the agent 232 and the data objects in the data model, examples will now be discussed.

A first example is shown in FIGS. 5A and B. Columns 500 a-x correspond to contact parts. Row 504 comprises contact part identifiers, row 508 the contact identifier of which the contact parts are members, row 512 the media type (with “V” indicating a live voice communication such as a telephone connection or Voice Over IP), rows 516 and 520 the start and stop times, respectively, of each contact part 500 a-x, row 524 the identity of the participant (with “A” being a first agent, “B” a second agent, and “C” the customer), row 528 the use of a multi-party conference, and row 532 the state of the monitored endpoint.

With reference to FIG. 5A, the customer telephone call is received by the contact center, such as by being assigned a VDN, and contact part 500 a is created for the customer endpoint making the contact. The state of the call changes to “qualification”, which represents processing of the call to select an appropriate resource to service the call. A second contact part 500 b is created as a result of the state change. The call state then changes to “queued” and a third contact part 500 c is created.

When the call reaches the head of the queue, the endpoint of the selected agent, namely agent A, is contacted and has the state “alerting” indicating that the agent's phone is ringing. A fifth contact part 500 d is created that corresponds to the endpoint of agent A. AT the same time, the state of the customer's endpoint changes from “queued” to “alerting”, indicating that the customer can hear a ring tone in his phone as the agent's endpoint is rung.

The agent answers the call and his state changes from “alerting” to “active” in a sixth contact part 500 e, and the customer's state also changes from “alerting” to “active” in a seventh contact part 500 f.

After a short discussion, the agent determines that the assistance of a second agent, namely agent B, is needed. The first agent places the customer on hold while he contacts the second agent. This sequence of events is reflected in the eighth through the twelfth contact parts 500 g-k in which the customer's status changes to “inactive” and the first agent's status changes to “inactive”, “initiating”, and “alerting”. A contact part 500 j is created for the second agent and corresponds to the “alerting” state.

The second agent answers the call so that his and the first agent's respective states each change to “active”. The first agent then joins the customer into the communication by removing the customer from hold. This is reflected in contact parts 500 l-p.

The second agent places the other parties on hold as reflected by contact part 500 q, while the other parties remain connected and active as reflected by contact part 500 r.

The first agent disconnects from the call as shown by contact part 500 s, leaving the customer on hold with the second agent.

The second agent takes the customer off hold in contact parts 500 t and u such that both the second agent and customer are “active”.

Finally, both the second agent and customer disconnect in contact parts 500 v and w, respectively.

The second example of FIGS. 6A and B depict contact parts resulting from a change in media. In contact parts 600 a-g, the customer and first agent are engaged in a chat session. In contact parts 600 h-i, the customer and agent change media to live voice. In contact parts 600 q and r, the first agent transfers the contact to the second agent and wraps up his part of the contact. In contact parts 600 s and t, the second agent and customer are engaged in a live voice communication. In contact parts 600 u and v, the second agent and customer are engaged in a chat session. Finally, in contact parts 600 w and x the second agent and customer disconnect.

A number of variations and modifications of the invention can be used. It would be possible to provide for some features of the invention without providing others.

For example, the server and/or switch can be a software-controlled system including a processing unit (CPU), microprocessor, or other type of digital data processor executing software or an Application-Specific Integrated Circuit (ASIC) as well as various portions or combinations of such elements. The memory may be a random access memory (RAM), a read-only memory (ROM), or combinations of these and other types of electronic memory devices.

The agent can be configured to obtain more detailed information about the remote party's endpoint. In the typical implementation, the agent infers or assumes information about the remote party due to a lack of information from the remote party's endpoint/network about parties, states, and media. For example, the remote endpoint could conference in another party or transfer the call to another endpoint without the knowledge of the tracking agent.

Any other suitable contact tracking algorithm may be employed. As will be appreciated, the algorithms of FIG. 4 is only exemplary and not intended to be exclusive or limiting. In particular, the contact tracking agent can be configured to track independently one or more of party, media, and state. Thus, the agent can create contact parts for only party changes, for only media changes, for only state changes, or for a combination thereof.

The present invention, in various embodiments, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various embodiments, subcombinations, and subsets thereof. Those of skill in the art will understand how to make and use the present invention after understanding the present disclosure. The present invention, in various embodiments, includes providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and/or reducing cost of implementation.

The foregoing discussion of the invention has been presented for purposes of illustration and description. The foregoing is not intended to limit the invention to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the invention are grouped together in one or more embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the invention.

Moreover though the description of the invention has included description of one or more embodiments and certain variations and modifications, other variations and modifications are within the scope of the invention, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter. 

1. In a contact center comprising a plurality of resources for servicing a plurality of contacts, the plurality of resources corresponding to a plurality of contact center endpoints, a method comprising: (a) at least one of receiving a first contact from an endpoint of a first customer and initiating the first contact to the first customer's endpoint; (b) creating, by a processor executable contact tracking agent and in connection with the first contact, a first contact part for the first customer endpoint, the first contact part describing the first customer, contact state of the first contact with reference to the first customer, and a communication channel of the first customer endpoint in the first contact; (c) connecting the first contact with a first contact center resource to service the first customer by the first contact center resource; (d) in response to step (c), creating, by the contact tracking agent and in connection with the first contact, a second contact part for the first contact center resource, the second contact part describing the first contact center resource, contact state of the first contact with reference to the first contact center resource, and a communication channel used by a first contact center endpoint associated with the first contact center resource, each of the first and second contact parts being related to the first contact; (e) while the first customer is serviced by the first contact center resource in the first contact, monitoring, by the contact tracking agent, each of the first customer endpoint and the first contact center endpoint for an occurrence of at least one of (i) a further change in contact state; (ii) a connection of the first contact center resource and the first customer by a new communication channel; and (iii) adding another party to the first contact and/or transferring the first contact to a new party; and (f) applying, by the contact tracking agent, at least one of the following rules: (F1) when at least one of (i) a further change in contact state and (ii) the connection of the first contact center resource and the first customer by a new communication channel occurs at one of the first customer endpoint and the first contact center endpoint, creating, by the contact tracking agent, a third contact part comprising an attribute of the occurrence, the third contact part being associated with the one of the first customer and first contact center resource and the first contact, wherein each of the first, second, and third contact parts comprises a plurality of common types of attributes; and (F2) when (iii) occurs, creating, by the contact tracking agent, a fourth contact part comprising an attribute of the occurrence, the fourth contact part being associated with the new party and the first contact, wherein each of the first, second, and fourth contact parts comprises a plurality of common types of attributes.
 2. The method of claim 1, wherein rule (F1) applies.
 3. The method of claim 2, wherein the at least one of (i) a further change in contact state and (ii) the connection of the first contact center resource and the first customer by a new communication channel has occurred at the first customer endpoint, but not the first contact center endpoint, and wherein the first contact part, but not the second contact part, is terminated and the third contact part is created, the first, second, and third contact parts being associated with the first contact.
 4. The method of claim 2, wherein a further change in contact state occurs.
 5. The method of claim 4, wherein the contact state in the first contact part changes from a first state to a second state, wherein the first and second contact parts temporally overlap, wherein a contact part related describes the relationship between the first and second contact parts, and wherein the first and second states are each one of active, inactive, queued, ringing, and terminating.
 6. The method of claim 1, wherein the first contact center resource and the first customer endpoints are connected through the new communication channel, and wherein each of the first and second contact parts comprises a plurality of the following attributes: contact type code, media code (which identifies the type of media/medium used during the contact part), contact part ID (which uniquely identifies the contact part), contact ID (which uniquely identifies the contact of which the contact part is a subpart), state ID (which identifies the state of the corresponding monitored endpoint to which the contact part corresponds), contact media interaction start datetime (the date/time that the contact media interaction started), party ID, business role code, party role start datetime, wait treatment ID, active media mask (a mapping of possible media types and their direction), contact part delivery source code, UCID (Universal Call Identifier), contact part datetime started (the date/time that the contact part started), contact part datetime stopped (the date/time that the contact part stopped), observing call flag, trunk ID, contact part routing method code, contact part purpose code, extension ID, routing construct ID, contact part subject (a text description of the subject of the message), contact participation group ID, contact direction code, malicious call flag, queue priority, login ID, login start date/time, data source ID, reschedule datetime (time stamp indicating when the contact connected to this part will be rescheduled to make another attempt), contact control indicator, state reason ID, calling number ID (the number dialed by the originator of the contact), and dialed number purpose ID.
 7. The method of claim 6, wherein the original and new communication channels are each different ones of an audio communication over the PSTN, voice-over-IP, text chat, instant messaging, a video stream, e-mail, facsimile, and voice messaging and wherein the second, but not the first, contact part is terminated in response to the occurrence of the at least one of (i) further change in contact state; (ii) connection of the first contact center resource and the first customer by the new communication channel; and (iii) adding another party to the first contact and/or transferring the first contact to a new party.
 8. The method of claim 2, wherein the contact tracking agent creates: a contact media interaction associated with the occurrence and the third contact part, a contact part purpose classifying a purpose of the first contact part, and a contact part related defining a reason for a relationship between the first and second contact parts, and wherein a set of data structures associated with the first contact is associated with a plurality of contact parts, the plurality of contact parts including the first, second, and third contact parts, each contact part being associated with only one of the first customer and first contact center resource.
 9. The method of claim 1, further comprising: (g) during the servicing of the first contact by the first contact center resource, monitoring the first customer's endpoint for the at least one of (i) further change in contact state and (ii) connection of the first contact center resource and the first customer by the new communication channel; and (h) identifying an occurrence of the at least one of (i) further change in contact state and (ii) connection of the first contact center resource and the first customer by the new communication channel; (i) in response to the occurrence, creating the occurrence as the third contact part.
 10. The method of claim 9, wherein the creating step (i) comprises: terminating the first contact part, but not the second contact part, and creating the third contact part, the first and third contact parts being associated with the first contact.
 11. The method of claim 1, wherein rule (F2) applies.
 12. The method of claim 11, wherein a contact participation group shows a relationship of the first, second, and fourth contact parts and wherein each of the first and second contact parts is associated with a plurality of a contact part related, contact participation group, contact part purpose, contact part related reason, contact media interaction, contact media interaction disposition, contact part qualifier, contact part delivery source, contact part disposition, contact part routing method, contact part wait treatment, contact qualifier, dialed number purpose, disposition, media, party login, routing construct, routing construct contact part, state reason, step, and step contact part.
 13. A non-transitory computer readable medium comprising processor executable instructions that, when executed, perform the steps of claim
 1. 14. A system, comprising: (a) a plurality of resources for servicing a plurality of contacts, the plurality of resources corresponding to a plurality of contact center endpoints, (b) an input operable to receive a first contact from an endpoint of a first customer and/or initiate the first contact to the first customer's endpoint; (c) a switching fabric operable to connect the first contact with a first contact center endpoint of a first contact center resource, the first contact center resource servicing the first customer during the connected first contact, wherein the connected first contact comprises a first communication medium, but not a second communication medium, between the first customer endpoint and the first contact center endpoint; (d) a contact tracking agent operable to: (D1) create, in connection with the first contact, a first contact part for the first customer endpoint, the first contact part describing the first customer, contact state of the first contact with reference to the first customer, and a first communication medium of the first customer endpoint in the first contact; (D2) create, in connection with the connected first contact, a second contact part for the first contact center resource, the second contact part describing the first contact center resource, contact state of the connected first contact with reference to the first contact center resource, and the first communication medium used by a first contact center endpoint, each of the first and second contact parts being related to the connected first contact; (D3) while the first customer is serviced by the first contact center resource in the connected first contact, monitor each of the first customer endpoint and the first contact center endpoint for an occurrence of at least one of (i) a further change in contact state; (ii) a connection of the first contact center resource and the first customer by the second communication medium; and (iii) adding another party to the connected first contact and/or transferring the connected first contact to a new party; and (D4) apply at least one of the following rules: (D4.1) when at least one of (i) a further change in contact state and (ii) the connection of the first contact center resource and the first customer by the second communication medium occurs at one of the first customer endpoint and the first contact center endpoint, create a third contact part comprising an attribute of the occurrence, the third contact part being associated with the one of the first customer and first contact center resource and the connected first contact, wherein each of the first, second, and third contact parts comprises a plurality of common types of attributes; and (D4.2) when (iii) occurs, create a fourth contact part comprising an attribute of the occurrence, the fourth contact part being associated with the new party and the connected first contact, wherein each of the first, second, and fourth contact parts comprises a plurality of common types of attributes.
 15. The system of claim 14, wherein rule (D4.1) applies.
 16. The system of claim 15, wherein the at least one of (i) a further change in contact state and (ii) the connection of the first contact center resource and the first customer by the second communication medium has occurred at the first customer endpoint, but not the first contact center endpoint, and wherein the first contact part, but not the second contact part, is terminated and the third contact part is created, the first, second, and third contact parts being associated with the connected first contact.
 17. The system of claim 15, wherein a further change in contact state occurs.
 18. The system of claim 17, wherein the contact state in the first contact part changes from a first state to a second state, wherein the first and second contact parts temporally overlap, wherein a contact part related describes the relationship between the first and second contact parts, and wherein the first and second states are each one of active, inactive, queued, ringing, and terminating.
 19. The system of claim 14, wherein the first contact center resource and the first customer endpoints are connected through the second communication medium.
 20. The system of claim 19, wherein the first and second communication mediums are each different ones of an audio communication over the PSTN, voice-over-IP, text chat, instant messaging, a video stream, e-mail, facsimile, and voice messaging and wherein the second, but not the first, contact part is terminated in response to the occurrence of the at least one of (i) further change in contact state; (ii) connection of the first contact center resource and the first customer by the second communication medium; and (iii) adding another party to the first contact and/or transferring the first contact to a new party.
 21. The system of claim 15, wherein a contact media interaction associated with the occurrence and the third contact part is created and wherein a contact part purpose classifies a purpose of the first contact part.
 22. The system of claim 14, wherein the contact tracking agent is further operable to: (E) during the servicing of the first customer by the first contact center resource, monitor the first customer's endpoint for the at least one of (i) further change in contact state and (ii) connection of the first contact center resource and the first customer by the second communication medium; (F) identify an occurrence of the at least one of (i) further change in contact state and (ii) connection of the first contact center resource and the first customer by the second communication medium; and (G) in response to the occurrence, create the occurrence as the third contact part.
 23. The system of claim 22, wherein the creating operation (G) comprises: terminating the first contact part, but not the second contact part, and creating the third contact part, the first and third contact parts being associated with the connected first contact.
 24. The system of claim 14, wherein rule (D4.2) applies.
 25. The system of claim 24, wherein a contact participation group shows a relationship of the first, second, and fourth contact parts.
 26. A method, comprising: (a) receiving, by a computer server, a first contact from an endpoint of a first customer; (b) connecting, by the server, the first contact with a first contact center endpoint of a first contact center resource; (c) creating, by a processor executable contact tracking agent, first and second contact parts for the first customer and first contact center endpoints, respectively, the first and second contact parts being related to the first contact; (d) determining, by the contact tracking agent, that at least one of (i) a change in state of the first contact, (ii) a change in communication medium used in the first contact, and (iii) a change in party participating in the first contact has occurred; (e) in response to step (d), terminating, by the contact tracking agent, one of the first and second contact parts; (f) in response to step (d), creating a third contact part, the third contact part being associated with the one of the first customer and contact center endpoints affected by the determined at least one of (i) a change in state of the first contact, (ii) a change in communication medium used in the first contact, and (iii) a change in party participating in the first contact.
 27. The method of claim 26, wherein, in step (e), the other one of the first and second contact parts is not terminated.
 28. The method of claim 26, wherein (i) is determined to have occurred, wherein the state change affects the first contact center endpoint but not the first customer endpoint, wherein, in step (e), the second contact part is terminated, and wherein, in step (f), the third contact part is associated with the first contact center endpoint but not the first customer endpoint.
 29. The method of claim 26, wherein (ii) is determined to have occurred, wherein the state change affects the first contact center endpoint and the first customer endpoint, wherein, in step (e), the first and second contact parts are terminated, wherein, in step (f), the third contact part is associated with the first contact center endpoint but not the first customer endpoint and further comprising creating a fourth contact part, the fourth contact part being associated with the first customer endpoint but not the first contact center endpoint.
 30. The method of claim 26, wherein (iii) is determined to have occurred, wherein the state change is a call transfer from the first contact center endpoint to a second contact center endpoint while the first customer endpoint is connected to the first contact, wherein, in step (e), the second, but not the first, contact part is terminated, wherein, in step (f), the third contact part is associated with the second contact center endpoint but not the first customer endpoint.
 31. A non-transient computer readable medium comprising processor executable instructions that, when executed, perform the steps of claim
 26. 32. The method of claim 31, wherein each of the first and second contact parts is associated with only one of the first customer and first contact center resource, a specific contact state, and a specific set of communication channels, wherein each of the first customer and first contact center resource may be associated with only one of the first and second contact parts at any point in time, wherein a set of data structures associated with the first contact is not altered when the third contact part is created, wherein the set of data structures has an identifier, wherein each of the first, second, and third contact parts comprises the identifier associated with the set of data structures, wherein each of the first, second, and third contact parts has a different identifier, and wherein the identifier associated with the set of data structures is different from the identifiers of the first, second, and third contact parts.
 33. The method of claim 26, wherein each of the first and second contact parts is associated with only one of the first customer and first contact center resource, a specific contact state, and a specific set of communication channels, wherein each of the first customer and first contact center resource may be associated with only one of the first and second contact parts at any point in time, wherein a set of data structures associated with the first contact is not altered when the third contact part is created, wherein the set of data structures has an identifier, wherein each of the first, second, and third contact parts comprises the identifier associated with the set of data structures, wherein each of the first, second, and third contact parts has a different identifier, and wherein the identifier associated with the set of data structures is different from the identifiers of the first, second, and third contact parts.
 34. The method of claim 26, wherein the contact tracking agent creates a contact part related defining a reason for a relationship between the first and second contact parts and wherein a set of data structures associated with the first contact is associated with a plurality of contact parts, the plurality of contact parts including the first, second, and third contact parts, each contact part being associated with only one of the first customer and resource.
 35. The method of claim 26, wherein each of the first and second contact parts is associated with a plurality of a contact part related, contact participation group, contact part purpose, contact part related reason, contact media interaction, contact media interaction disposition, contact part qualifier, contact part delivery source, contact part disposition, contact part routing method, contact part wait treatment, contact qualifier, dialed number purpose, disposition, media, party login, routing construct, routing construct contact part, state reason, step, and step contact part.
 36. The method of claim 26, wherein each of the first and second contact parts comprises a plurality of the following attributes: contact type code, media code (which identifies the type of media/medium used during the contact part), contact part ID (which uniquely identifies the contact part), contact ID (which uniquely identifies the contact of which the contact part is a subpart), state ID (which identifies the state of the corresponding monitored endpoint to which the contact part corresponds), contact media interaction start datetime (the date/time that the contact media interaction started), party ID, business role code, party role start datetime, wait treatment ID, active media mask (a mapping of possible media types and their direction), contact part delivery source code, UCID (Universal Call Identifier), contact part datetime started (the date/time that the contact part started), contact part datetime stopped (the date/time that the contact part stopped), observing call flag, trunk ID, contact part routing method code, contact part purpose code, extension ID, routing construct ID, contact part subject (a text description of the subject of the message), contact participation group ID, contact direction code, malicious call flag, queue priority, login ID, login start date/time, data source ID, reschedule datetime (time stamp indicating when the contact connected to this part will be rescheduled to make another attempt), contact control indicator, state reason ID, calling number ID (the number dialed by the originator of the contact), and dialed number purpose ID.
 37. The method of claim 26, wherein a contact part is associated with only one of the first customer and first contact center resource, a specific contact state, and a specific set of communication channels, wherein each of the first customer and first contact center resource may be associated with only one contact part at any point in time, wherein a set of data structures associated with the first contact is not altered when the second contact part is created, wherein the set of data structures has an identifier, wherein each of the first and second contact parts comprises the identifier associated with the set of data structures, and wherein the identifier associated with the set of data structures is different from the identifiers of the first and second contact parts.
 38. The system of claim 14, wherein the contact tracking agent creates a contact part related defining a reason for a relationship between the first, second, and third contact parts and wherein a set of data structures associated with the first contact is associated with a plurality of contact parts, the plurality of contact parts including the first and second contact parts, each contact part being associated with only one of the first customer and resource.
 39. The system of claim 14, wherein each of the first and second contact parts is associated with a plurality of a contact part related, contact participation group, contact part purpose, contact part related reason, contact media interaction, contact media interaction disposition, contact part qualifier, contact part delivery source, contact part disposition, contact part routing method, contact part wait treatment, contact qualifier, dialed number purpose, disposition, media, party login, routing construct, routing construct contact part, state reason, step, and step contact part.
 40. The system of claim 14, wherein each of the first and second contact parts comprises a plurality of the following attributes: contact type code, media code (which identifies the type of media/medium used during the contact part), contact part ID (which uniquely identifies the contact part), contact ID (which uniquely identifies the contact of which the contact part is a subpart), state ID (which identifies the state of the corresponding monitored endpoint to which the contact part corresponds), contact media interaction start datetime (the date/time that the contact media interaction started), party ID, business role code, party role start datetime, wait treatment ID, active media mask (a mapping of possible media types and their direction), contact part delivery source code, UCID (Universal Call Identifier), contact part datetime started (the date/time that the contact part started), contact part datetime stopped (the date/time that the contact part stopped), observing call flag, trunk ID, contact part routing method code, contact part purpose code, extension ID, routing construct ID, contact part subject (a text description of the subject of the message), contact participation group ID, contact direction code, malicious call flag, queue priority, login ID, login start date/time, data source ID, reschedule datetime (time stamp indicating when the contact connected to this part will be rescheduled to make another attempt), contact control indicator, state reason ID, calling number ID (the number dialed by the originator of the contact), and dialed number purpose ID. 